Skip to main content

📄 Monitoring Guide

TODO

Missing content under the H1 (this) section.

1. Introduction to Monitoring at API3​

At API3, monitoring extends beyond traditional systems to encompass decentralized APIs (dAPIs), APIs, and on-chain activities. These components are at the core of our DAO's operations.

Monitoring in our context involves:

  • Observing dAPI Activities: Keep a close eye on the performance, responsiveness, and health of dAPIs.
  • Logging API Events: APIs are the backbone of data exchange. Monitoring them ensures that data feeds are uninterrupted, accurate, and timely.
  • Triggering On-chain Alerts: Given the immutable and transparent nature of blockchains, on-chain activities need to be observed for discrepancies, failures, or unusual patterns. These can provide early warning signs of potential issues or threats.

The purpose of this document is to guide our monitoring team through the nuances of overseeing API3's ecosystem. Armed with this knowledge, the team can make informed decisions, respond swiftly to anomalies, and uphold the high standards that our users and stakeholders have come to expect.

2. General Monitoring Guidelines​

  1. Stay Vigilant: Regularly review Centurion, Opsgenie and Slack channels. Being proactive can prevent small issues from escalating.
  2. Systematic Approach: Always follow established protocols. In the face of multiple alerts, prioritize based on severity and potential impact.
  3. Communication:
    • Establish clear communication channels within the Monitoring team and any other technical teams involved.
    • In the event of system outages or major disruptions, ensure everyone is informed to manage the situation better.
  4. Documentation:
    • Keep detailed records of all monitoring activities, including false alarms.
    • This can be valuable for refining monitoring parameters and improving system resilience.
  5. Stay Updated:
    • Join #monitoring-team and other relevant communication channels.
    • Regularly check for any announcements or updates that can impact monitoring.
  6. Feedback:
    • If you notice any potential improvements in the monitoring process, tools, or systems, share feedback with the team.

3. Tools​

4. Other Things to Monitor​

  • The UptimeRobot Slack bot monitors the following URLs:

    If any of these go down, the UptimeRobot Slack bot will send a message to the #monitoring-team channel.

  • Centurion sends alerts simultaneously to both Opsgenie and the #centurion-alerts Slack channel. If Opsgenie goes down, alerts can still be seen in the Slack channel.

Owner: UNKOWN
Last updated on by Warren Anderson